-
Notifications
You must be signed in to change notification settings - Fork 454
CDRIVER-4689 Additional partial implementation of OIDC authentication #2018
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Note, I've been debugging the mock-server-test failure but I'm not confident I'll be able to provide a solution before my accounts lock at some unspecified time. The failure is in |
I won't have time to test and push a fix for the
|
With this patch:
This backtrace shows the problem (which at this point is no longer a segfault, but a parameter assert deeper in the stack)
Note where we require a URI to test the auth mechanism. I haven't had a chance yet to look closely enough at the scanner's life cycle to determine where we're best off fixing this. It's possible this might be addressed in a way that also relates to the larger problem of tests not having a good single source of truth about the intended auth mechanism. |
In the specific case of the mock server test, it would seem like we could defer creating the scanner until we know the first URI. If this behavior is actually desirable more generally, maybe it would make sense to have a |
Here's a simple fix:
|
This branch is pushed to https://github.com/mongodb/mongo-c-driver/tree/OIDC-CDRIVER-4689. The branch was added to the |
This is my attempt to revive a patch stack that Kyle Kloberdanz was working on about 1 year ago. Kyle has since left MongoDB. Unrelatedly, I'm also leaving. (To protest the "AI" hype here.) My last day will be this Wednesday May 21st and I'm losing access to my corporate accounts. This GitHub account will be deleted before I lose access, so if this PR won't be merged by then someone will need to copy the branch if the work is to be continued.
The commit stack is a bit harrowing and I would not recommend reviewing commit-by-commit. My process here was to (very interactively) rebase an old copy of Kyle's branch on main, while editing out changes that conflicted with the intervening work on OIDC callbacks. After the rebase, I added commits intended to fix specific problems as described in the messages.
What's maybe good?
What's a problem:
What's just incomplete: